Skip to main content

This is a new service – your feedback will help us to improve it.

Royal Borough of Kensington and Chelsea

Article 4 direction area

There is a problem

  • 84 issue of type invalid category value

Article 4 - No 71

reference
55
name
Article 4 - No 71
article-4-direction
55
permitted-development-rights

undefined

Minor alterations in Conservation Areas including works to windows
uprns
address-texts
geometry
MULTIPOLYGON (((-0.162240 51.490400,-0.162250 51.490420,-0.162340 51.490480,-0.162350 51.490480,-0.162480 51.490400,-0.162370 51.490320,-0.162240 51.490400)),((-0.160820 51.491320,-0.160850 51.491300,-0.160860 51.491310,-0.161010 51.491230,-0.160880 51.491140,-0.160730 51.491220,-0.160730 51.491240,-0.160820 51.491320)),((-0.161020 51.491070,-0.161170 51.491170,-0.161230 51.491140,-0.161300 51.491090,-0.161350 51.491070,-0.161400 51.491110,-0.161460 51.491070,-0.161700 51.490950,-0.161850 51.490860,-0.161940 51.490820,-0.162050 51.490750,-0.162130 51.490710,-0.162090 51.490680,-0.162130 51.490660,-0.162160 51.490660,-0.162180 51.490650,-0.162150 51.490630,-0.162170 51.490620,-0.162140 51.490590,-0.162170 51.490570,-0.162140 51.490550,-0.162170 51.490530,-0.162100 51.490480,-0.162030 51.490510,-0.161550 51.490770,-0.161320 51.490910,-0.161080 51.491030,-0.161020 51.491070)))
point
POINT (-0.161625 51.490844)
notes
entry-date
2025-01-03
start-date
end-date

How to fix this issue

Your dataset is missing the permitted-development-rights column.

The Article 4 direction area guidance explains how to fix the issue:

permitted-development-rights

A list of the permitted development rights withdrawn by the article 4 direction.

Separate the rights in the list using semicolons.

Only use rights from our permitted development right dataset. If the area withdraws a permitted development right that is not in our dataset, email digitalland@communities.gov.uk.

Example: 3D;3M;11B

How to improve Royal Borough of Kensington and Chelsea’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL